Re: [Freesafe-users] JFreeSafe updates/build problems

[Alexandre K. <ako...@ya...>]

Laszlo, 
   sorry for the disturbance. I was able to
successfully modify,build, and install the app using
the 0.2.7 source. I was originally checking the app
from cvs and getting the 0.2.6.1 sources, which I was
able to get to build the jar; however, I was getting
an "Invalid jar" message when I attempted to install
the jar. After installing 0.2.7, I did notice that on
the site you had a notice that there were some
problems installing 0.2.6.1... is that the same
problem or something different ? 

   I was thinking that I should post this type of
message in the mailing list as I thought it might be
useful for anyone else having a similar type of
problem. 

Thanks, 

Alex K

--- Alexandre Kotchnev <ako...@ya...> wrote:

> Laszlo, 
>   thanks for your response to my question on
> sourceforge
>
(https://sourceforge.net/forum/forum.php?thread_id=1511446&forum_id=226494).
> 
> 
>   Sorry that it took me so long to respond.
> Initially,
> I was checking the topic on sourceforge almost
> daily,
> but since I didn't get a response, I kinda lost hope
> and stoped checking :-) 
> 
>   For starters, I was just wondering - if you check
> out of sources from cvs and change the path to the
> WTK, do you get a successful build ? If not, would
> be
> able to commit the latest sources to CVS ? I've
> checked out the sources from CVS; however, I can't
> get
> it to build properly. I change the properties to
> point
> to my wtk 1.0.4 setup; however, it keeps failing in
> the obfuscation and preverification step. Initially,
> it can't find the parent classes for some of the
> test
> classes in the cldc_crypto.jar (so, I had to remove
> the bouncycastle test package as it seems to depend
> on
> classes that are not in cldc). I wouldn't want to
> waste your time to give you all the error messages,
> I
> should be able to sort things out myself. 
> 
> 
>  
> >> I was just wondering if you have considered  
> >> switching the password field on the  
> >> PasswordEntry.DetailsDialog to TextField.ANY 
>  
> > Yes, I have. I know it is quite inconvenient on
> some
> models. I own a Nokia 9500 with a full qwverty
> keyboard so it's a non issue for me :) 
> 
> I have a Nokia E61 and the input is pretty easy on
> it
> as well; however, i want to be able to view the
> whole
> content at the same time, instead of having to
> scroll
> through one letter at a time. As long as I can do a
> successful build, I'll make the necessary changes
> and
> provide patches. 
> 
>  
> > Alternatively, I could create a FreeNoteEntry  
> > with the appropriate dialog for editing that  
> > would just hold a "Title" and a "Note". Let me  
> > know which approach you think is better and I  
> > can submit a patch.  
>  
> >That's also an old request from some users and I
> have
> >already made a promise to do it. My ethernal excuse
> is >that I want to finish the backup facility first,
> but >now I can see that it will be put aside for a
> while. >So yes, doing it sounds reasonable. But wait
> a
> few  >days please, because I'm not sure that what I
> have in >the CVS is the absolute latest version. 
> 
> I would love to contribute a patch to this - I just
> need to get it to build first. 
>  
> > Along these lines, I was having a bit of trouble 
> >getting the build to work straight out of cvs. I  
> > changed the property in build.properties to  
> > point to my wtk install (btw, what wtk version  
> > do you use ? ) 
>  
> >Yep, I use a rather old one (1.0.4). It has a
> >different structure that v2 has. v1 had a
> midpapi.zip
> >somewhere (see the build.properties file) while v2
> has >midp10.jar, midp20.jar, cldc10.jar and
> cldc11.jar. >(And you have to choose one midpxx and
> one cldcxx >jar.) 
>  
> >I'll update the build file to use the newer j2mewtk
> >(I've already done it for my work projects). BTW
> the
> >concept with the build system is that you don't
> change >the build.properties file (because it goes
> into the >CVS) but create a build.local.properties
> and
> tweak >that. 
> 
>    Thanks for the tip. I do think it would be a good
> idea to upgrade the build to use WTK2, but WTK 1
> also
> works OK.
>  
>  
> >Yes, I know. But when I started out this project
> >(autumn of 2003) it didn't have all that support.
> It
> >would have been a lot easier to use the new and
> fancy
> >dialog and flow designer (though my solution with
> the
> >dialog manager concept and the stacked screens is a
> >bit cleaner :) but harder to use than the IDE RAD).
> 
>  
>    Do you use NetBeans for development or something
> else ? 
> 
> > get the regular ant build working when it's  
> > checked out of 
>  
> I'll fix it to work with j2mewtk v2. If you want to
> play around in the meantime, all you have to do is
> including the midp10.jar and cldc10.jar in the
> bootclasspath (replace midpapi.zip to them in the
> build files). 
>  
> Laszlo (btw I prefer e-mail, you can reach me at
> at...@at...) 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com