[...] Can this be an inheritance thing? Also: [...] If you have CCR, someone else could have invalidated the object in the meantime. The DBC actually *does* a fetch, so it stands to reason that actually nothing was returned... maybe you can turn on SQL logging after your [...]]]>
WebObjects is embedded, and here's the full stack trace: :) 2009-11-23 17:27:46,048 FATAL -[7345:2020 3] Application (?:?) - Application -1 handled exception: No com.chello.dbkit.eo.CBPageTemplate found with globalID: <PageTemplate: [templateId: '1011'] > er.extensions.eof. [...]]]>
Well, I do need a new session, because I use the session to handle the current documents, just like a shopping-cart. I use ERXJSOpenWindowHyperlink to start a directAction, but I always get the same session. Frank Op 24-nov-2009, om 03:35 heeft email@hidden het volgende geschreven: On Nov 23, 2009, at 2:06 PM, Frank Stock wrote: > quoted text [...]]]>
Here is my recent email on this matter: http://lists.apple.com/archives/Webobjects-dev/2009/Nov/msg00459.html The fix works fine for us, although I've jadded _NSWeakMutableArray only - since we didn't have any issues with other subclasses. So, what would be the proper way to commit the fix? [...]]]>
Would you like to go with *Shark* - Apple in-built profiler? Cheers, Shravan Kumar. M ------------------------------------- Tuesday, November 24, 2009 8:04:28 AM From: "Kieran Kelleher" <email@hidden> To: "Kieran Kelleher" <email@hidden> [...]]]>
Never mind. Solved my problem with Shark and logging...... there goes my once every year "wish I had JProfiler" episode ;-) Regards, Kieran :-) On Nov 23, 2009, at 9:34 PM, Kieran Kelleher wrote: And if I just go into Launch Configs, make a new WOApplication (JProfiler) config and try tp launch it, I get: An internal error occurred during: "Launching cheetah". com.jprofiler.integrations.eclipse.internal.ProfilingSession.createProfilingSession(Lorg/eclipse/debug/core/model/ILaunchConfigurationDelegate;Lorg/eclipse/debug/core/ILaunchConfiguration;)Lcom/jprofiler/integrations/eclipse/internal/ProfilingSession; On Nov 23, 2009, at 9:28 PM, Kieran Kelleher wrote: Need a profiler for a weird memory issue. The trial key only works with JProfiler 6. Installed JProfiler, and latest 3.4.XXX nightly wolips and JProfiler support. Restarted eclipse with -clean. The context menu for Profile As.. does not have a WOApplication item. .... any hints on what else to get JProfiler going? Regards, Kieran On Nov 17, 2009, at 5:19 PM, Mike Schrag wrote: I've never tried with 6, which just came out ... I'm on 5.x. ms On Nov 17, 2009, at 5:18 PM, Lon Varscsak wrote: I spoke too soon. :) Is there a specific version of JProfiler I need? I get this error: java.lang.NoSuchMethodError: com.jprofiler.integrations.eclipse.internal.ProfilingSession.createProfilingSession(Lorg/eclipse/debug/core/model/ILaunchConfigurationDelegate;Lorg/eclipse/debug/core/ILaunchConfiguration;)Lcom/jprofiler/integrations/eclipse/internal/ProfilingSession; at org.objectstyle.wolips.jprofiler.launching.JProfilerWOJavaLocalApplicationLaunchConfigurationDelegate.launch(JProfilerWOJavaLocalApplicationLaunchConfigurationDelegate.java:71) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) On Tue, Nov 17, 2009 at 3:14 PM, Lon Varscsak <email@hidden> wrote: Ah, step #2 was my problem. Thanks Mike. -Lon On Tue, Nov 17, 2009 at 2:57 PM, Mike Schrag <email@hidden> wrote: > quoted text
]]>And if I just go into Launch Configs, make a new WOApplication (JProfiler) config and try tp launch it, I get: An internal error occurred during: "Launching cheetah". com.jprofiler.integrations.eclipse.internal.ProfilingSession.createProfilingSession(Lorg/eclipse/debug/core/model/ILaunchConfigurationDelegate;Lorg/eclipse/debug/core/ILaunchConfiguration;)Lcom/jprofiler/integrations/eclipse/internal/ProfilingSession; On Nov 23, 2009, at 9:28 PM, Kieran Kelleher wrote: Need a profiler for a weird memory issue. The trial key only works with JProfiler 6. Installed JProfiler, and latest 3.4.XXX nightly wolips and JProfiler support. Restarted eclipse with -clean. The context menu for Profile As.. does not have a WOApplication item. .... any hints on what else to get JProfiler going? Regards, Kieran On Nov 17, 2009, at 5:19 PM, Mike Schrag wrote: I've never tried with 6, which just came out ... I'm on 5.x. ms On Nov 17, 2009, at 5:18 PM, Lon Varscsak wrote: I spoke too soon. :) Is there a specific version of JProfiler I need? I get this error: java.lang.NoSuchMethodError: com.jprofiler.integrations.eclipse.internal.ProfilingSession.createProfilingSession(Lorg/eclipse/debug/core/model/ILaunchConfigurationDelegate;Lorg/eclipse/debug/core/ILaunchConfiguration;)Lcom/jprofiler/integrations/eclipse/internal/ProfilingSession; at org.objectstyle.wolips.jprofiler.launching.JProfilerWOJavaLocalApplicationLaunchConfigurationDelegate.launch(JProfilerWOJavaLocalApplicationLaunchConfigurationDelegate.java:71) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:866) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1069) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) On Tue, Nov 17, 2009 at 3:14 PM, Lon Varscsak <email@hidden> wrote: Ah, step #2 was my problem. Thanks Mike. -Lon On Tue, Nov 17, 2009 at 2:57 PM, Mike Schrag <email@hidden> wrote: > quoted text
]]>Need a profiler for a weird memory issue. The trial key only works with JProfiler 6. Installed JProfiler, and latest 3.4.XXX nightly wolips and JProfiler support. Restarted eclipse with -clean. The context menu for Profile As.. does not have a WOApplication item. .... [...]]]>
Hi Lachlan; I'm using JUL logging, but I turned that off to explicitly avoid interference. Oh well; I was able to get SQL logging on the database product to get the diagnostics I needed in this case. cheers. [...]]]>
[...] Are you using log4j? This is what I've got in my log4j config: log4j.rootLogger=INFO, A1 [...] log4j.logger.NSLog=DEBUG with regards,]]>
Hi Chuck; Thanks for that. I tried what you have done in code as well as; -DEOAdaptorDebugEnabled=true -DNSDebugGroups="(NSLog.DebugGroupSQLGeneration,NSLog.DebugGroupDatabaseAccess,NSLog.DebugGroupEnterpriseObjects)" -DNSDebugLevel=NSLog.DebugLevelDetailed [...]]]>
You've probably changed the NSLog Group or Level. Here is what I use
to turn this on in code:
public static void logSQL(boolean shouldLog)
{
if (shouldLog)
{
NSLog.allowDebugLoggingForGroups(NSLog.DebugGroupSQLGeneration [...]]]>I thought you did too, but when I went to look I could not find it. But I threw away the message which I would not have done if you had not committed the fix. Chuck On Nov 23, 2009, at 2:24 PM, Mike Schrag wrote: It's not fixed in 5.4.3, but I thought we fixed it in Wonder? [...]]]>
It's not fixed in 5.4.3, but I thought we fixed it in Wonder? On Nov 23, 2009, at 4:37 PM, Lon Varscsak wrote: I get these too in one production app (where a lot of insertions and deletes are going on)...but it's intermittent. I saw a post somewhere that someone said it was fixed, but I don't think it made it into 5.4.3. It's really annoying and I had to start restarting that app once a day automatically to avoid the error. If you learn anything to fix this, please shoot me an email. Good luck, Lon On Mon, Nov 23, 2009 at 10:08 AM, Dominique Schoenenberger <email@hidden> wrote: [...]]]>
Hello; I have used this many times prior, but it's got me today; -DEOAdaptorDebugEnabled=true I can't seem to get out the SQL trace -- I know there's gotchas around this one. Can anybody remember how to make this one work? cheers. ___ Andrew Lindesay www.lindesay.co. [...]]]>
[...] Why do you need a new session? Just give the user a link that opens the app in a second browser window (target="_blank"). If you are managing your editing contexts in a reasonable manner, there is no need for one session == one browser window. [...]]]>
Hello Frank; You could pass basic session information between the instances and then allow a trusted token to initiate a new session on an other instance other than the one on which the user was previously working. cheers. [...]]]>
Hi all, I want to be able to create a new session, so once the user has logged in and is working in one session, he should be able to open a new session, but without logging in again. I need this because if a user is for instance creating an invoice and the phone is going, so he can create another session to search the data and then later continue to work with the older session. Thanks in advance, Frank Stock Belgium]]>
[...] I am not sure that I believe you. :-) Can you paste in the full error message and complete stack trace? [...] Is WebObjects embedded? Could there be a different version on that Solaris machine? Chuck -- Chuck Hill Senior Consultant / VP Development [...]]]>
I get these too in one production app (where a lot of insertions and deletes are going on)...but it's intermittent. I saw a post somewhere that someone said it was fixed, but I don't think it made it into 5.4.3. It's really annoying and I had to start restarting that app once a day automatically to avoid the error. If you learn anything to fix this, please shoot me an email. Good luck, Lon On Mon, Nov 23, 2009 at 10:08 AM, Dominique Schoenenberger <email@hidden> wrote: [...]]]>
[...] Porter is cheap and convenient too. [...] Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld [...]]]>
Le 09-11-23 à 15:45, Chuck Hill a écrit : On Nov 23, 2009, at 11:59 AM, Calven Eggert wrote: [...] Especially with VIA, it can get really cheap when you reserve a couple of months before your trip. Chuck On 2009-11-23, at 2:22 PM, David Avendasora wrote: [...]]]>
[...] I co-host the local cocoa heads meetings which occur quarterly <http://tacow.org>. We have a few past and present WO devs in regular attendance. And yeah, WOWODC is very much worth the cost of attending. ;david]]>
[...] Montreal is not that far away and WOWODC is pretty good value for what you learn. Chuck On 2009-11-23, at 2:22 PM, David Avendasora wrote: On Nov 23, 2009, at 2:13 PM, Pascal Robert wrote: Le 09-11-23 à 14:05, Calven Eggert a écrit : [...] I think you have that backwards. [...]]]>
We drink here BECAUSE our teams don't win anything, anywhere, anytime. Ironically, I'm not a drinker so I have to actually feel the pain of our loser teams. BTW - I'm a Calgary Flames fan. On 2009-11-23, at 3:07 PM, Pascal Robert wrote: Le 09-11-23 à 14:59, Calven Eggert a écrit : > quoted text
Oh yes, Wonder, Entity Modeler and the component editor now finds a hell lot of errors that the old tools didn't catch up. It's a lot of work to fix those, but it will improve your apps. > quoted text
Toronto, the city where none of your sports teams wins anything? :-) But at least you still have a baseball team... Calven On 2009-11-23, at 2:22 PM, David Avendasora wrote: On Nov 23, 2009, at 2:13 PM, Pascal Robert wrote: Le 09-11-23 à 14:05, Calven Eggert a écrit : > quoted text
I think you have that backwards. With the NewHotness WOLips (from last January), for DEVELOPMENT you don't need a compiled framework in Library/Frameworks, but if you are going to use WOLips Ant Tools -> Install to DEPLOY your application, then you do need a fully compiled version of your Frameworks in /Library/Frameworks. With that said, Hudson is a much better way to go about building for deployment than using WOLips Ant Tools -> Install. Dave So the steps is : when you are ready to deploy, run a Ant install on your framework, after run the Ant install on your app and your framework should be embed in your app just like Wonder and the WO frameworks. I think David A. covered this in his WOWODC West session. hmmm, how to I make this right? On 2009-11-23, at 1:42 PM, Pascal Robert wrote: Embed your frameworks (and any other frameworks) into your app and you won't have to worry about /Library/Frameworks anymore. Right-click on your project name -> Properties, and in the WOLips Deploy, check the boxes to say that you want to embed local and system frameworks. Run the ant install again and your app will now have all needed frameworks inside itself. Ah, the Project.name= entry was NOT filled in in the build.properties file and so that fixed the problem of my Framework not appearing. Thanks for that. The problem now is that installing my app on the server can't find the framework and this time IT IS located in /Library/Frameworks because I put it there on the server. I know this because I get the error "java.lang.NoClassDefFoundError" for a class in my framework. My original WO application projects are from a long time ago and so I suspect that this may be the problem. I am using build.xml files from newly created WO projects in eclipse. What should I check for in my build settings to make sure the WO app is connecting to the framework properly? (The app runs no problem from eclipse) Current configuration: Eclipse 3.4.2 WO5.4.3 WOLips from here(http://webobjects.mdimension.com/wolips/stable) Java 1.5 Wonder 54 binaries > quoted text
Calven On 2009-11-23, at 12:07 PM, David LeBer wrote: On 2009-11-23, at 11:51 AM, Calven Eggert wrote: > quoted text
[...]
Are you sure? Did you check the /Library/Framworks with the terminal (ls -al)? You might find a .frameworks folder with the correct creation/mod time. That would mean that you are missing the project.name= entry in your project's build.properties. If that is the case, how old was the WOLips you were updating from? > quoted text
[...]
]]>
Le 09-11-23 à 14:59, Calven Eggert a écrit : > quoted text
Oh yes, Wonder, Entity Modeler and the component editor now finds a hell lot of errors that the old tools didn't catch up. It's a lot of work to fix those, but it will improve your apps. [...]]]>Thanks All! I'm able to install my app on the server now with or without my framework embedded. It seems that sometimes the build will not find the framework on my machine until I quit eclipse, restart it and then do a clean. not sure why. Has anyone else found this problem? [...]]]>
[...] UTF-8 please. UTF8 is an old/incorrect definition. [...]]]>
On Nov 23, 2009, at 2:13 PM, Pascal Robert wrote: Le 09-11-23 à 14:05, Calven Eggert a écrit : > quoted text
I think you have that backwards. With the NewHotness WOLips (from last January), for DEVELOPMENT you don't need a compiled framework in Library/Frameworks, but if you are going to use WOLips Ant Tools -> Install to DEPLOY your application, then you do need a fully compiled version of your Frameworks in /Library/Frameworks. With that said, Hudson is a much better way to go about building for deployment than using WOLips Ant Tools -> Install. Dave So the steps is : when you are ready to deploy, run a Ant install on your framework, after run the Ant install on your app and your framework should be embed in your app just like Wonder and the WO frameworks. I think David A. covered this in his WOWODC West session. hmmm, how to I make this right? On 2009-11-23, at 1:42 PM, Pascal Robert wrote: Embed your frameworks (and any other frameworks) into your app and you won't have to worry about /Library/Frameworks anymore. Right-click on your project name -> Properties, and in the WOLips Deploy, check the boxes to say that you want to embed local and system frameworks. Run the ant install again and your app will now have all needed frameworks inside itself. Ah, the Project.name= entry was NOT filled in in the build.properties file and so that fixed the problem of my Framework not appearing. Thanks for that. The problem now is that installing my app on the server can't find the framework and this time IT IS located in /Library/Frameworks because I put it there on the server. I know this because I get the error "java.lang.NoClassDefFoundError" for a class in my framework. My original WO application projects are from a long time ago and so I suspect that this may be the problem. I am using build.xml files from newly created WO projects in eclipse. What should I check for in my build settings to make sure the WO app is connecting to the framework properly? (The app runs no problem from eclipse) Current configuration: Eclipse 3.4.2 WO5.4.3 WOLips from here(http://webobjects.mdimension.com/wolips/stable) Java 1.5 Wonder 54 binaries > quoted text
Calven On 2009-11-23, at 12:07 PM, David LeBer wrote: On 2009-11-23, at 11:51 AM, Calven Eggert wrote: > quoted text
[...]
Are you sure? Did you check the /Library/Framworks with the terminal (ls -al)? You might find a .frameworks folder with the correct creation/mod time. That would mean that you are missing the project.name= entry in your project's build.properties. If that is the case, how old was the WOLips you were updating from? > quoted text
[...]
David Avendasora Senior Software Engineer K12, Inc. ***** WebObjects Documentation Wiki : http://wiki.objectstyle.org/confluence/display/WO/ ***** WebObjects API: http://developer.apple.com/legacy/mac/library/documentation/MacOSXServer/Reference/WO54_Reference/index.html *****
]]>
Le 09-11-23 à 14:05, Calven Eggert a écrit : > quoted text
No need to include your framework as a project in the Build Path, you should add it as a WebObjects Library Framework, just like other frameworks instead. In 3.4, this is where the major change was done. [...]]]>hmmm, I did that, checked off the local/system frameworksin WOLips Deploy and the install includes all the libraries except mine. :-( Looks like the Build path stuff is wrong. In the Projects tab I include my project folder and in the Libraries Tab I added myframework. [...]]]>
Embed your frameworks (and any other frameworks) into your app and you won't have to worry about /Library/Frameworks anymore. Right-click on your project name -> Properties, and in the WOLips Deploy, check the boxes to say that you want to embed local and system frameworks. [...]]]>
Ah, the Project.name= entry was NOT filled in in the build.properties file and so that fixed the problem of my Framework not appearing. Thanks for that. The problem now is that installing my app on the server can't find the framework and this time IT IS located in /Library/Frameworks because I put it there on the server. I know this because I get the error "java.lang.NoClassDefFoundError" for a class in my framework. My original WO application projects are from a long time ago and so I suspect that this may be the problem. I am using build.xml files from newly created WO projects in eclipse. What should I check for in my build settings to make sure the WO app is connecting to the framework properly? (The app runs no problem from eclipse) Current configuration: Eclipse 3.4.2 WO5.4.3 WOLips from here(http://webobjects.mdimension.com/wolips/stable) Java 1.5 Wonder 54 binaries > quoted text
Calven On 2009-11-23, at 12:07 PM, David LeBer wrote: On 2009-11-23, at 11:51 AM, Calven Eggert wrote: > quoted text
[...]
Are you sure? Did you check the /Library/Framworks with the terminal (ls -al)? You might find a .frameworks folder with the correct creation/mod time. That would mean that you are missing the project.name= entry in your project's build.properties. If that is the case, how old was the WOLips you were updating from? > quoted text
[...]
]]>On Nov 23, 2009, at 9:07 AM, David LeBer wrote: On 2009-11-23, at 11:51 AM, Calven Eggert wrote: [...] Did you also change WOLips or Eclipse versions? If you updated to WOLips New Hotness, did you also update your build.xml files? Chuck [...] [...]]]>
I got this error in a production application (It was happening only in dev before), see error below This was already discussed in this mailing list but no solution was suggested. Does anybody found a way to avoid this problem or to fix it ? Or is this occurring sometimes and people are living with it ? Dominique Caused by: java.lang.StackOverflowError at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176) at com .webobjects .foundation ._NSWeakMutableArray.__removeReference(_NSWeakMutableArray.java:124) at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176) at com .webobjects .foundation ._NSWeakMutableArray.__removeReference(_NSWeakMutableArray.java:124) at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176) at com .webobjects .foundation ._NSWeakMutableArray.__removeReference(_NSWeakMutableArray.java:124) at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176) at com .webobjects .foundation ._NSWeakMutableArray.__removeReference(_NSWeakMutableArray.java:124) at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176) at com .webobjects .foundation ._NSWeakMutableArray.__removeReference(_NSWeakMutableArray.java:124) at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176) at com .webobjects .foundation ._NSWeakMutableArray.__removeReference(_NSWeakMutableArray.java:124) at com .webobjects .foundation ._NSWeakMutableCollection.processQueue(_NSWeakMutableCollection.java: 176)]]>
[...] Did you check the /Library/Framworks with the terminal (ls -al)? You might find a .frameworks folder with the correct creation/mod time. That would mean that you are missing the project.name= entry in your project's build.properties. If that is the case, how old was the WOLips you were updating from? [...] Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld]]>
Hi Calven, Before we get started with troubleshooting this can you answer a few questions: What versions of WO, WOLips and Eclipse are you using? How did you install WebObjects on Snow Leopard? What are the contents of ~/Library/Application Support/WOLips/wolips.properties? [...]]]>
Just another couple of ideas:
Regarding (4) below, If your project doesn't use Wonder, then in your
Application constructor, do this:
WOMessage.setDefaultEncoding("UTF8");
Regarding (5), if you're using HTML 4.01 Transitional, then it might
look something like this:
<! [...]]]>I just updated to Snow Leopard last week and I'm having trouble building my WO framework and projects. The first build I attempt is my framework. It builds with no errors, although lots of warnings like ...should be parameterized, but when I do the install the framework is NOT in the /Library/Frameworks folder. It is in the /Build folder, but looking in there, in the .framework/Resources/Java folder the .jar is not there. hmmm Here is the output: Buildfile: /Users/ceggert/Projects/COREFW/build.xml init.properties: init.install: init.build: compile: build.woframework: [woframework] Installing in /Library/Frameworks javaclient: install: BUILD SUCCESSFUL Total time: 873 milliseconds I do have the wolips.properties in ~/Library/Application Support/WOLips. I have read the last two articles here (http://wolips.blogspot.com/) but I can't say i fully understand it all. Any suggestions? Calven]]>
If you want to see the list of recordings you can purchase from past WOWODC without creating an account just to see the list, you can look at it here : http://wocommunity.org/apps/WebObjects/WOCommunity.woa/wa/recordings ---- Pascal Robert email@hidden AIM: MacTICanada [...]]]>
Good catch, I meant sorting with ERXArrayUtilities. I'll try the one-liner, was looking to optimize that series of calls anyway, so thanks for that! We're using the same database, same drivers. Enabling SQL debugging shows that when the EOObjectNotAvailableException is thrown, there was in fact no prior SQL call made. We're likely missing something (of course, otherwise it probably would be working), but it looks like EOF gives up on the fault of the object when sorting. The database isn't even queried to verify if the object with that ID exists (which it does). -Ben On Nov 23, 2009, at 4:31 PM, David Avendasora wrote: [...]]]>
[...] "filter that array" You aren't _filtering_ the array, you are sorting it. Since you are using Wonder and the Wonder eogenerator templates, you can achieve the same in one line by: NSArray myArrayOfEntities = Entity.fetchEntities(editingContext, qualifier, sortOrderings); [...]]]>
It does not, the sort is based on a name attribute of the entity. -Ben On Nov 23, 2009, at 4:07 PM, Ken Anderson wrote: [...]]]>
Ben, Does the sort include any relationships? Ken On Nov 23, 2009, at 9:59 AM, Lawson, Ben wrote: [...]]]>
Hey guys, hoping maybe one of you can shed light on this issue we've been having intermittently: We start by fetching all the rows out of a table using EOUtilities.objectsForEntityNamed(editingContext, entityName), and then filter that array with ERXArrayUtilities. [...]]]>
MMM so I guess I will install 3.4 then. On Nov 23, 2009, at 3:00 PM, Kieran Kelleher wrote: [...]]]>
Whether it works or not, you are running an untested, unsupport configuration. Supported configs are: Eclipse 3.4.2 with wolips 3.4.XXXX Eclipse 3.5 with wolips 3.5.XXXX (and this is still considered experimental until Mike Schrag gives it the "thumbs up") [...]]]>
Hello. well at the office I used to have 3.4 and wolips 3.4.xxx installed, all worked there perfect. (even its discouraged) Now i had to migrate the workspace to my personal machine, and ther eI have installed (dunno why, long time ago I had it) snow leopard, eclipse galileo, and I saw the wolips version 3.4.5950, I migrated the workspace, fixed some build paths, ran the application Im working on, and it works.. it loads the app.. perfect. Now reading some old post where it says one should be using E3.5 with WOlips 3.5 version, does this means I will have problems in the future if I leave this configuration? should I change to Wolips 3.5? not stable yet with E 3.5,?, as I read in some post.? Thx Gustavo]]>
Hi! That's sad... IIRC, I started learning Cocoa when I was young and stupid (now, I'm just stupid) with a stepwise article published in the MacTech magazine. It was during the Mac OS X early age, I was still graduating, and it gave me a much more comprehensive introduction that [...]]]>
Right - so who set up wotips? Is there any way to lock this down? On 23/11/2009, at 9:28 AM, Chuck Hill wrote: [...]]]>