<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/atrisframework/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/atrisframework/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/atrisframework/feature-requests/</id><updated>2008-01-28T13:47:51Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>object selection framework</title><link href="https://sourceforge.net/p/atrisframework/feature-requests/4/" rel="alternate"/><published>2008-01-28T13:47:51Z</published><updated>2008-01-28T13:47:51Z</updated><author><name>Markus Elfring</name><uri>https://sourceforge.net/u/elfring/</uri></author><id>https://sourceforge.net2657768fbf3d522eb0bd5dfb22e97d7e0dcb6f38</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Your software deals with the following features.&lt;br /&gt;
- multiple object selection techniques&lt;br /&gt;
- bounding box calculation&lt;br /&gt;
- grid snapping, magnetic areas&lt;br /&gt;
- triggering feedback to the user&lt;/p&gt;
&lt;p&gt;Would you like to offer any component that can be reused as a class library on its own in other applications?&lt;br /&gt;
How much are the existing interfaces reusable already?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Use Hibernate as Persistence Layer</title><link href="https://sourceforge.net/p/atrisframework/feature-requests/3/" rel="alternate"/><published>2003-11-25T09:42:17Z</published><updated>2003-11-25T09:42:17Z</updated><author><name>Jürgen Hoffmann</name><uri>https://sourceforge.net/u/buddy1974/</uri></author><id>https://sourceforge.net19747df2499e815d5339a5584574a08ddb7c1bfe</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have just roughly read the docs. Would it be possible &lt;br /&gt;
to use hibernate as a persistencelayer within your &lt;br /&gt;
framework in 2-tier architectures? I think this would &lt;br /&gt;
improve performance, because these folks do nothing &lt;br /&gt;
else, than develop the O/R Mapper, and it has very good &lt;br /&gt;
reputation.&lt;/p&gt;
&lt;p&gt;Kind regards&lt;/p&gt;
&lt;p&gt;Jürgen Hoffmann&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Smart component resizing</title><link href="https://sourceforge.net/p/atrisframework/feature-requests/2/" rel="alternate"/><published>2003-10-23T19:35:35Z</published><updated>2003-10-23T19:35:35Z</updated><author><name>Kevin Self</name><uri>https://sourceforge.net/u/kself/</uri></author><id>https://sourceforge.nete1e9421fbb82b68ea80d52aeb014ff36fba7ecf5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When the user resizes a screen manually with the drag &lt;br /&gt;
bars, the components currently stay in fixed positions. &lt;br /&gt;
The components should 'float' to relative positions on &lt;br /&gt;
the new screen dimension (depending on the object &lt;br /&gt;
type).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Smart initial window sizing</title><link href="https://sourceforge.net/p/atrisframework/feature-requests/1/" rel="alternate"/><published>2003-10-23T19:34:21Z</published><updated>2003-10-23T19:34:21Z</updated><author><name>Kevin Self</name><uri>https://sourceforge.net/u/kself/</uri></author><id>https://sourceforge.netb29c863494575e3468d4b0143159c8e450f13067</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When opening a new window (for the first time), the &lt;br /&gt;
framework should compute the 'best' initial size based on &lt;br /&gt;
the components contained on its surface, and not set &lt;br /&gt;
up an initial windows size for every window that is &lt;br /&gt;
opened.&lt;/p&gt;
&lt;p&gt;Once opened, the window currently remembers its &lt;br /&gt;
dimensions so this is not a problem.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>