Hi Jaroslav,
I have finished to develop a first version of my framework and now I'm
doing some test. It seems to work. Also I'm writing some examples with
a little doc. Later on I will do it available and I will send you
Regards
Paolo
Il giorno 14/nov/07, alle ore 19:05, Jaroslav Hanus h
Hello Paolo
Could you please give me some more info concerning your data-GUI XML
binding approach? It seems to fit perfectly into our idea where to
move now with JC stuff. Although Florian's way is also nice and I
have found interesting info in his tutorial, this GUI - data
separation I w
Paolo,
I see why you like a more dynamic approach. Dynamic is good, and it
should not be very difficult to make a visual editor for your XML.
Since I have never extensively used EOAssociation classes, and have
after some initial work with it skipped Apple's JC stuff in total
(except when
Argh, I shouldn't have relied on my memory.
What I meant was the WebServicesAssistant.app, which is only a WOA
that is repackaged as an app. Sorry. But then I don't know why D2JC
is deprecated at all, except that all the cocoa components are most
likely broken and they didn't want to provid
Hi Florijan,
it's because the core jc stuff still stays that I think It's
reasonable to continue to use in the jc application EODisplayGroup,
EOAssociation, etc. I think the status is like as the web WO where the
core stuff stays but WebObjects Builder is lacking. In the jc client
develop
Hey Anjo,
Can you give me more information or examples of getting assistant to
use normal WO files? That would help me a lot right now. I would also
very much like to try to get D2JC unDEpreciated even if it does
remain unAppreciated. :)
Thanks,
Dave
On Nov 4, 2007, at 2:56 PM, Anjo Kra
Thanks to all, and apologies as well, last time I checked (a few days
ago) I was unable to locate the 5.4 API online, possibly to my own
stupidity.
My best,
Flor
On Nov 07, 2007, at 14:09, Mike Schrag wrote:
Could we stop the speculation and look at the facts. The
documentation is here:
h
Could we stop the speculation and look at the facts. The
documentation is here:
http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/
.. and also
http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/deprecated-list.html
ms
__
On 7-Nov-07, at 12:32 PM, Florijan Stamenkovic wrote:
Hm, one might think that if a number of developers are wondering
about the same point, the release notes might be somewhat confusing.
And that the vendor (and it's respected representatives) might be
considered nice if they would polite
Could we stop the speculation and look at the facts. The documentation
is here:
http://developer.apple.com/documentation/MacOSXServer/Reference/WO54_Reference/
Pierre
--
Pierre Frisch
[EMAIL PROTECTED]
On Nov 7, 2007, at 9:32, Florijan Stamenkovic wrote:
Hm, one might think that if a number
Hm, one might think that if a number of developers are wondering
about the same point, the release notes might be somewhat confusing.
And that the vendor (and it's respected representatives) might be
considered nice if they would politely clarify the point (an action
taking a total of 2 min
I do not respond to shouts. Just look in the documentation. What is
deprecated is marked, it if is not marked it is not deprecated.
Pierre
--
Pierre Frisch
[EMAIL PROTECTED]
On Nov 7, 2007, at 7:37, Florijan Stamenkovic wrote:
Hi all,
Great to see some JC discussions going on :)
Uhm, her
Hi all,
Great to see some JC discussions going on :)
Uhm, here is my two cents. Let's all do whatever we can to get a
straight answer from Apple about the core JC being depreciated or
not. Cliff Tuel NOT being the WO Apple person on the list anymore, I
do not know whom can be directly con
sorry, I forgot Interface Builder ...
Il giorno 05/nov/07, alle ore 16:57, Paolo Sommaruga ha scritto:
Hi,
we are in production some nib based jcs. Such jcs are complex
enough. Therefore in order to migrate in a world without
Interface Builder
we need to use the existing code as much as
Hi,
we are in production some nib based jcs. Such jcs are complex enough.
Therefore in order to migrate in a world without we need to use the
existing code as much as possible in order to avoid altering the
entire applications. Besides a great deal of Apple jc stuff works well
even thoug
Am 01.11.2007 um 20:33 schrieb David Avendasora:
I know I'm planning on digging into it soon because a large portion
of my application is D2JC, which will need to be replaced.
Again: D2JC is deprecated, but wrongly so. If you know how to write
individual components by hand, then you should
Mike Schrag stated in the "State of the Union" thread:
* My understanding is that JavaClient stuff is technically still
there, but there's not very good tool support for it. NetBeans
project file support for Entity Modeler would allow the combination
of Entity Modeler plus the Swing desi
Mike Schrag stated in the "State of the Union" thread:
* My understanding is that JavaClient stuff is technically still
there, but there's not very good tool support for it. NetBeans
project file support for Entity Modeler would allow the combination
of Entity Modeler plus the Swing desig
And I have EXACTLY the same question. We develop and maintain quite a
huge application with two frontends - html WebObjects for extranet
users and Java Client for intranet. For JC we used the NIB-Based IB
development, although with quite a lot of hacks to force it to work
the way we needed.
Okay, I have the same question as John and Flor, and I don't think
it's been answered yet. For those of you NOT doing regular Java
Client (I guess there a few ;) there have been THREE ways of doing WO
JC development in the past:
1) D2JC
2) NIB-Based using Interface Builder
3) Straight Swing
All I'm saying is that you can get D2JC to still work by fixing up the
package to a plain WO app. However, my uneducated guess is that there
won't be much development going on with the Java client stuff.
Cheers, Anjo
Am 31.10.2007 um 13:38 schrieb John Pollard:
I am not quite clear on what
Hi Anjo,
I am not quite clear on what you are saying. I am not concerned about
the Java interface for which we happen to use JFormDesigner at
present. I really want to know whether the EOF / distribution jars
are deprecated - the ones that let me write code on the client side,
almost as i
The D2JC stuff still works if you replace the binary in the assistant
package with a normal WO launch script. IB is pretty much dead for WO
dev, but you can code your own components or write some GUI editor for
it (or reuse the stuff other editors create for you).
Cheers, Anjo
Am 31.10.200
Deprecations in WO5.4:
Java Client Nib based applications
Direct to JavaClient based applications
Does this mean the end of Java Client full stop? We use Java Client
but NOT Nibs or Direct To. Our Java interface is pure swing.
What we do depend on is basically the distributed EOF functionali
24 matches
Mail list logo
