In times of people being always online, and AJAX technology available, I think it would be best to move keepass online as it is the place where passwords are needed.
How hard is it to "convert/reinvent/compile" the code to make it an online application?
Are there any plans yet of such a version?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use KeePass at work and at least 50% of my requirements are not on-line. At home it is mainly on-line, so having KeePass as a stand-alone application suits me just fine.
Re-building it as an AJAX app would probably be best achieved by starting from scratch as KeePass is written in C# - not a small task.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't mean to be rude or anything, but what IS the point of having an online version ?
I mean, you get :
- less security
- less reactivity
- unavailability of the database whenever you are *not* online
- and, I suspect, less compatibility (I really don't see a browser-integrated tool, be it AJAX or not, capable of auto-typing in another browser for one thing, let alone auto-typing in just about any application opened on your machine)
I can see the cons, so could you please direct me towards the pros ?
I am as technology-enthousiast as any of us, but on this particular issue I can't see which goal is pursued, I really can't.
Fashion trend ?
Thanks :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In times of people being always online, and AJAX technology available, I think it would be best to move keepass online as it is the place where passwords are needed.
How hard is it to "convert/reinvent/compile" the code to make it an online application?
Are there any plans yet of such a version?
I use KeePass at work and at least 50% of my requirements are not on-line. At home it is mainly on-line, so having KeePass as a stand-alone application suits me just fine.
Re-building it as an AJAX app would probably be best achieved by starting from scratch as KeePass is written in C# - not a small task.
cheers, Paul
Hello.
I don't mean to be rude or anything, but what IS the point of having an online version ?
I mean, you get :
- less security
- less reactivity
- unavailability of the database whenever you are *not* online
- and, I suspect, less compatibility (I really don't see a browser-integrated tool, be it AJAX or not, capable of auto-typing in another browser for one thing, let alone auto-typing in just about any application opened on your machine)
I can see the cons, so could you please direct me towards the pros ?
I am as technology-enthousiast as any of us, but on this particular issue I can't see which goal is pursued, I really can't.
Fashion trend ?
Thanks :)