July 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] ODBC on W7 and Pharo 1.4

by Friedrich Dominicus

"Torsten Bergmann" <astares(a)gmx.de> writes: >>But it does not declare anything which is needed e.g for >>understanding SQLDouble and the like. > > Because FFI is a general callout mechanism for native APIs > and the ODBC package is just implemented on top of it. You are right, but it does not declare the handling of pointer or I have not understand it. > Just by looking at the code, maybe > - #initializeDataTypes has a wrong definition > - maybe the ODBCConstants definition is wrong > - maybe #initializeResultSet:number: has a problem Well I did exactly what you suggested and the problem is very likely in here: checkSQLReturn: (ODBCLibrary default sqlDescribeCol: resultSetHandle columnNumber: number columnName: columnName bufferLength: BUFFERSIZE nameLength: nameLenght dataType: columDataType columnSize: columnSize decimalDigits: decimalDigits nullable: columnNullable) The problem here is that columnSize gives 53 with Access 2003. and this surely is wrong it may even be a problem in Access for ages because I found a hotfix for it for Access 2007 http://www.everythingaccess.com/tutorials.asp?ID=The-lowdown-on-Access-2007 I guess this may explain my problem. Anyway I'm not sure about it. So to me it seems this is a problem in the ODBC Driver vor Access, but I could not imagine that no-one ever have treated Doubles while trying to access MS Access with Pharo. > >>Sorry, does that mean the name I gave to the Data source must be placed >>in host? > > Yes, that worked for me. "host" is a bit misleading - for an > SQLite connection it can be the local path, for ODBC its the DSN name > for a network database it is the hostname or IP address. Sorry having a Database name in host is all but obvious. Regards Friedrich

July 26, 2012

Re: [Pharo-project] RPackage registration mess

by Camillo Bruni

On 2012-07-26, at 13:24, Guillermo Polito wrote: > My bad :/. > > BTW, we have to introduce one method to restore the system subscriptions to > a good state whatever was the state before. And that way we do not mess it > so easily again. but the strange part is, that this cannot be caused by tests... I saw that some tests did it wrong. still strange that it popped up again :/

July 26, 2012

Re: [Pharo-project] RPackage registration mess

by Guillermo Polito

My bad :/. BTW, we have to introduce one method to restore the system subscriptions to a good state whatever was the state before. And that way we do not mess it so easily again. On Thu, Jul 26, 2012 at 1:17 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > so once again rpackage is registered to the wrong announcer... > > I figured out that update 20200 first introduced this bug by wrongly > resetting RPackage: > > http://code.google.com/p/pharo/issues/detail?id=6326 > > It registered RPackageOrganizer to MCWorkingCopy announcer but > > SystemAnnouncer announcer == MCWorkingCopy announcer > > and by default RPackageOrganizer registers to SystemAnnouncer > privateAnnouncer. > > obviously we got a double registration of RPackageOrganizer after this. > Which can be easily fixed by doing: > > RPackageOrganizer registerInterestToSystemAnnouncement. > > The invariant that should hold is > > > self assert: SystemAnnouncer announcer hasSubscriber: > RPackageOrganizer default = false. > self assert: SystemAnnouncer privateAnnouncer hasSubscriber: > RPackageOrganizer default. > > however I still can't figure out where the damn bug got introduced again... > until a few updates ago, the RPackage tests were not restoring the SystemAnnouncer correctly on tearDown. Probably it was in there...

July 26, 2012

Re: [Pharo-project] RPackage registration mess

by Damien Cassou

On Thu, Jul 26, 2012 at 1:17 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > self assert: SystemAnnouncer announcer hasSubscriber: RPackageOrganizer default = false. this expression is probably incorrect as #= is sent to (RPackageOrganizer default) -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 26, 2012

[Pharo-project] RPackage registration mess

by Camillo Bruni

so once again rpackage is registered to the wrong announcer... I figured out that update 20200 first introduced this bug by wrongly resetting RPackage: http://code.google.com/p/pharo/issues/detail?id=6326 It registered RPackageOrganizer to MCWorkingCopy announcer but SystemAnnouncer announcer == MCWorkingCopy announcer and by default RPackageOrganizer registers to SystemAnnouncer privateAnnouncer. obviously we got a double registration of RPackageOrganizer after this. Which can be easily fixed by doing: RPackageOrganizer registerInterestToSystemAnnouncement. The invariant that should hold is self assert: SystemAnnouncer announcer hasSubscriber: RPackageOrganizer default = false. self assert: SystemAnnouncer privateAnnouncer hasSubscriber: RPackageOrganizer default. however I still can't figure out where the damn bug got introduced again...

July 26, 2012

Re: [Pharo-project] ODBC on W7 and Pharo 1.4

by Guillermo Polito

On Thu, Jul 26, 2012 at 12:35 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >But it does not declare anything which is needed e.g for > >understanding SQLDouble and the like. > > Because FFI is a general callout mechanism for native APIs > and the ODBC package is just implemented on top of it. > > So why should the FFI docu cover the ODBC stuff? > FFI docu just describes how to call external libs (written in C or > others). > > The ODBC package is nothing more than a wrapper around > some Win32 API functions like SQLAllocEnv, etc. The docu > for them can be found in MSDN (just Google). > > If you want to track problems in the ODBC package > check the code and see if it does correct callouts > and use correct data types according to Microsoft specs. > > Just by looking at the code, maybe > - #initializeDataTypes has a wrong definition > - maybe the ODBCConstants definition is wrong > - maybe #initializeResultSet:number: has a problem > > You should debug your problem since you have a reproducable case > or switch to a newer, more supported package like DBXTalk with > an active mailinglist. > > >Sorry, does that mean the name I gave to the Data source must be placed > >in host? > > Yes, that worked for me. "host" is a bit misleading - for an > SQLite connection it can be the local path, for ODBC its the DSN name > for a network database it is the hostname or IP address. > > Yes! I know it is misleading, the thing is we've made only one common protocol for every database. Specific methods to be more friendly to special cases like SQLite ODBC are maybe a good idea, isn't it? :^) > >I'm sorry but how should one know that? > > Note that is a general interface to databases. You can not > assume that the developers of OpenDBX/DBXTalk test any kind > of database (here MS Access) and give you a docu for database > specific connections. > DBXTalk covers typical relational databases used in enterprise these > days (oracle, MSSQL, MySQL, ...), includes tests > and its nice to have such an initiative. > > Yeap, the normal cases are covered in the docs in the website. For specific stuff I recommend you to have a look at the tests... > >So what am I supposed to write into database? A table name? > > Did you try to leave it blank or use the same name as the DB? > > If I were you I would create a simple DB with Access with a > simple predefined table. Then setup the ODBC connection and > try to connect to it. If that works do a simple query. > If that communication works it should be no problem to > create/query tables from Smalltalk. However - if you have > DBXTalk specific questions switch to the DBXTalk mailinglist > > (http://dbxtalk.smallworks.com.ar then "Support") > > Yeap, you're welcome to subscribe :). Then again, if you want to have a look at some DBX examples, you can have a look at the tests. In particular, a connection example to a MSSQL database over ODBC can be found in DBXOdbcMSSQLFacility>>createConnection in the package OpenDBXDriverTests. It looks like: DBXConnectionSettings host: 'MSSQL' port: '3004' database: 'sodbxtest' userName: 'crapodino' userPassword: 'florynano'. I really don't know how this will behave with Access (I don't have access installed either :/). If you can give it a try and provide us any idea we can put it into the tests/website :). Bye > T. > >

July 26, 2012

[Pharo-project] ODBC on W7 and Pharo 1.4

by Torsten Bergmann

>But it does not declare anything which is needed e.g for >understanding SQLDouble and the like. Because FFI is a general callout mechanism for native APIs and the ODBC package is just implemented on top of it. So why should the FFI docu cover the ODBC stuff? FFI docu just describes how to call external libs (written in C or others). The ODBC package is nothing more than a wrapper around some Win32 API functions like SQLAllocEnv, etc. The docu for them can be found in MSDN (just Google). If you want to track problems in the ODBC package check the code and see if it does correct callouts and use correct data types according to Microsoft specs. Just by looking at the code, maybe - #initializeDataTypes has a wrong definition - maybe the ODBCConstants definition is wrong - maybe #initializeResultSet:number: has a problem You should debug your problem since you have a reproducable case or switch to a newer, more supported package like DBXTalk with an active mailinglist. >Sorry, does that mean the name I gave to the Data source must be placed >in host? Yes, that worked for me. "host" is a bit misleading - for an SQLite connection it can be the local path, for ODBC its the DSN name for a network database it is the hostname or IP address. >I'm sorry but how should one know that? Note that is a general interface to databases. You can not assume that the developers of OpenDBX/DBXTalk test any kind of database (here MS Access) and give you a docu for database specific connections. DBXTalk covers typical relational databases used in enterprise these days (oracle, MSSQL, MySQL, ...), includes tests and its nice to have such an initiative. >So what am I supposed to write into database? A table name? Did you try to leave it blank or use the same name as the DB? If I were you I would create a simple DB with Access with a simple predefined table. Then setup the ODBC connection and try to connect to it. If that works do a simple query. If that communication works it should be no problem to create/query tables from Smalltalk. However - if you have DBXTalk specific questions switch to the DBXTalk mailinglist (http://dbxtalk.smallworks.com.ar then "Support") Bye T.

July 26, 2012

[Pharo-project] Focus / Selection on PluggableTextMorph

by Goubier Thierry

Hi, would someone knows why the behavior of PluggableTextMorph is a bit strange with selections ? I'm using Spec and Pharo 2.0. 1 - Selecting text is Ok, blue color. Matches on the selected text elsewhere in the text morph are green. 2 - Switching to another window desactivate the selection, but maintains the matches in green (including where the selection was : it changes from blue to green). 3 - Clicking on the title of the window with the text morph... removes the green matches. So now, seemingly, there is nothing selected anymore ? 4 - Wrong! Moving back the mouse over the text morph brings back the selection (blue) and the matches (green) ! 5 - Opening a menu on the morph (right-click) also makes the selection disappear apparently. For fun, you can also do 1 - 5 - 4 and see your selection appear / disappear. So is this a feature or a bug ? How to turn it of ? 5- is very fun, because I was trying to build a menu where items are enabled depending on a selection or no selection, and, you can guess what happened : open the menu, 'et voilÃ ', no more selection -> everything disabled ! close the menu, and the selection is back :-( Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

July 26, 2012

Re: [Pharo-project] markdown to latext and html

by Camillo Bruni

markdown / pandoc work pretty well for that :) http://johnmacfarlane.net/pandoc/ I use it for all non-paper text. Plus you can simply output a .tex file and put it into a real latex document if needed. On 2012-07-25, at 22:04, Tudor Girba wrote: > The Pier Book offers this pretty much out of the box. > > Doru > > > On 25 Jul 2012, at 11:22, StÃ©phane Ducasse wrote: > >> Hi >> >> To support the publication in pdf and html directly, plus let people not to bother about latex, >> I would really to experiment the following for the next chapters of books. >> I do not know well markdown but I would like to know if the following makes sense. >> >> I would like to see if we can use markdown (plus some extensions for in text annotation, figure definition) >> as pivot language and to be able to generate latex and html from it. >> >> From a simple analysis of current chapter here are the needs: >> >> structure >> title (with ref) >> section (with ref) >> subsection >> paragraph >> itemize/enumerate >> code snippet (with ref) >> figure with caption and ref >> >> inside a text area >> link >> code >> index >> comment for editor >> citation >> reference >> >> I probably miss some of them but this is the core and we can reduce the number from the latex stand point. >> What do you think? Does markdown support the item above. >> Is the petitMarkdown parser working? Because I would like to write a visitor that generates the latex we use for the book. >> >> I would like to use Zinc documentation as a test. >> >> Stef >> >> > > -- > www.tudorgirba.com > > "Being happy is a matter of choice." > > > >

July 26, 2012

Re: [Pharo-project] ODBC on W7 and Pharo 1.4

by Friedrich Dominicus

"Torsten Bergmann" <astares(a)gmx.de> writes: > The below works for me with MSSQL Server > > settings := DBXConnectionSettings > host: 'NAME' > port: '' > database: 'MyDatabase' > userName: 'user' > userPassword: 'pass'. > platform := DBXOdbcBackend new. > connection := DBXConnection platform: platform settings: settings. > connection connect. > connection open. Sorry, does that mean the name I gave to the Data source must be placed in host? I'm sorry but how should one know that? The .mdb driver points to one file (the database) itself and in this database there are the different tables. So what am I supposed to write into database? A table name? Regards Friedrich

July 26, 2012